First Node, Communication Device, and Methods Performed Thereby for Handling Positioning Information

ABSTRACT

A method performed by a first node ( 111 ) is described herein. The first node ( 111 ) operates in a communications network ( 10 ). The first node ( 111 ) sends ( 204 ) a query to a second node ( 112 ) operating in the communications network ( 10 ). The query requests information on a location of a communication device ( 130 ) operating in the communications network ( 10 ). The communication device ( 130 ) is identified by the first node ( 111 ) as a constrained communication device ( 130 ) lacking a capability to query the second node ( 112 ). The first node ( 111 ) obtains ( 205 ) the information from the second node ( 112 ), in response to the sent query, and initiates updating ( 207 ) an object in the communication device ( 130 ) based on the obtained information. A method performed by the communication device ( 130 ) is also described, whereby the device sends ( 301 ), to the first node ( 111 ), an indication that it is constrained, and obtains ( 304 ) the update.

TECHNICAL FIELD

The present disclosure relates generally to a first node and methodsperformed thereby for handling positioning information. The presentdisclosure also relates generally to a communications device, andmethods performed thereby for supporting handling positioninginformation. The present disclosure further relates generally to acomputer program product, comprising instructions to carry out theactions described herein, as performed by the first node, or thecommunication device. The computer program product may be stored on acomputer-readable storage medium.

BACKGROUND

Computer systems may comprise one or more nodes. A node may comprise oneor more processors which, together with computer program code mayperform different functions and actions, a memory, a receiving and asending port. A node may be, for example, a server. Nodes may becomprised in a communications network.

Nodes within a communications network may be wireless devices, e.g.,stations (STAs), User Equipments (UEs), mobile terminals, wirelessterminals, terminals, and/or Mobile Stations (MS). Wireless devices areenabled to communicate wirelessly in a cellular communications networkor wireless communication network, sometimes also referred to as acellular radio system, cellular system, or cellular network. Thecommunication may be performed e.g. between two wireless devices,between a wireless device and a regular telephone, and/or between awireless device and a server via a Radio Access Network (RAN), andpossibly one or more core networks, comprised within thetelecommunications network. Wireless devices may further be referred toas mobile telephones, cellular telephones, laptops, or tablets withwireless capability, just to mention some further examples. The wirelessdevices in the present context may be, for example, portable,pocket-storable, hand-held, computer-comprised, or vehicle-mountedmobile devices, enabled to communicate voice and/or data, via the RAN,with another entity, such as another terminal or a server.

The communications network may cover a geographical area which may bedivided into cell areas, each cell area being served by another type ofnode, a network node or Transmission Point (TP), for example, an accessnode such as a Base Station (BS), e.g. a Radio Base Station (RBS), whichsometimes may be referred to as e.g., evolved Node B (“eNB”), “eNodeB”,“NodeB”, “B node”, or BTS (Base Transceiver Station), depending on thetechnology and terminology used. The base stations may be of differentclasses such as e.g. Wide Area Base Stations, Medium Range BaseStations, Local Area Base Stations and Home Base Stations, based ontransmission power and thereby also cell size. A cell is thegeographical area where radio coverage is provided by the base stationat a base station site. One base station, situated on the base stationsite, may serve one or several cells. Further, each base station maysupport one or several communication technologies.

In 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE),base stations, which may be referred to as eNodeBs or even eNBs, may bedirectly connected to one or more core networks. All data transmissionin LTE is controlled by the radio base station.

The standardization organization 3GPP is currently in the process ofspecifying a New Radio Interface called NR or 5G-UTRA, as well as aFifth Generation (5G) Packet Core Network, which may be referred to asNext Generation Core Network, abbreviated as NG-CN, NGC or 5G CN.

Internet of Things (IoT)

The Internet of Things (IoT) may be understood as an internetworking ofcommunication devices, e.g., physical devices, vehicles, which may alsoreferred to as “connected devices” and “smart devices”, buildings andother items—embedded with electronics, software, sensors, actuators, andnetwork connectivity that may enable these objects to collect andexchange data. The IoT may allow objects to be sensed and/or controlledremotely across an existing network infrastructure.

“Things,” in the IoT sense, may refer to a wide variety of devices suchas heart monitoring implants, biochip transponders on farm animals,electric clams in coastal waters, automobiles with built-in sensors, DNAanalysis devices for environmental/food/pathogen monitoring, or fieldoperation devices that may assist firefighters in search and rescueoperations, home automation devices such as the control and automationof lighting, heating, e.g. a “smart” thermostat, ventilation, airconditioning, and appliances such as washer, dryers, ovens,refrigerators or freezers that may use WiFi for remote monitoring. Thesedevices may collect data with the help of various existing technologiesand then autonomously flow the data between other devices.

Machine Type Communication (MTC)

Machine Type Communication (MTC) has, especially in the context of theInternet of Things (IoT), shown to be a growing market segment. An MTCdevice may be a communication device, typically a wireless communicationdevice or simply wireless device, that is a self and/or automaticallycontrolled unattended machine and that is typically not associated withan active human user in order to generate data traffic. An MTC devicemay be typically more simple, and typically associated with a morespecific application or purpose, than, and in contrast to, aconventional mobile phone or smart phone.

MTC involves communication in a wireless communication network to and/orfrom MTC devices, in which communication typically may be of quitedifferent nature and with other requirements than communicationassociated with e.g. conventional mobile phones and smart phones. In thecontext of the IoT it is evident that MTC traffic will be increasing andthus needs to be increasingly supported in wireless communicationsystems.

Constrained Application Protocol (CoAP)

Some of the devices that may make use of IoT or MTC may be consideredconstrained devices. A constrained device or constrained node may beunderstood as a node where some of the characteristics of Internet nodesmay not be attainable, often due to cost constraints and/or physicalconstraints on characteristics such as size, weight, and available powerand energy. For example, a constrained device may be a sensor in a caror in a building.

The Constrained Application Protocol (CoAP) may be understood as ageneric Representational State Transfer (REST) application Protocol forconstrained devices. It may be understood as defined in RFC7252. CoAPmay be considered to enable constrained devices to communicate with thewider Internet using similar protocols. CoAP is designed to be used overUser Datagram Protocol (UDP), which is described in RFC0768, over theInternet.

On actual deployments of CoAP, variants like Lightweight Machine toMachine Protocol (LWM2M) are becoming increasingly popular in order tomanage devices in a RESTful fashion.

LWM2M may be understood to provide a simple mechanism for devicemanagement of IoT Devices. It may provide interfaces for InformationReporting, Service Enablement, Firmware Updates and a generic way tosecurely manage a device.

In existing methods, the functionality of constrained devices is ratherbasic, given the limited capabilities of these devices. For example,most constrained devices lack positioning functionality. Therefore,factoring positioning information into the management functions of thesedevices is not possible.

SUMMARY

It is an object of embodiments herein to improve the communication ofconstrained devices in a communications network. It is a particularobject of embodiments herein to enable the provision of locationservices to constrained devices lacking positioning capability.

According to a first aspect of embodiments herein, the object isachieved by a method performed by a first node. The first node operatesin a communications network. The first node sends a query to a secondnode. The second node operates in the communications network. The queryrequests information on the location of the communication device. Thecommunication device operates in the communications network. Thecommunication device is identified by the first node as a constrainedcommunication device lacking a capability to query the second node. Thefirst node obtains the information from the second node, in response tothe sent query. The first node initiates updating an object in thecommunication device based on the obtained information.

According to a second aspect of embodiments herein, the object isachieved by a method performed by a communication device. Thecommunication device operates in the communications network. Thecommunication device is a constrained communication device. Thecommunication device sends, to the first node operating in thecommunications network, the indication that the communication device isa constrained communication device. The communication device obtains,from the first node and based on to the sent indication, the update inthe object in the communication device. The update comprises theinformation on the location of the communication device. Thecommunication device lacks the capability to query the second node. Thesecond node operates in the communications network and has access to thelocation information. The information in the obtained update originatesin the second node.

According to a third aspect of embodiments herein, the object isachieved by the first node, configured to operate in the communicationsnetwork. The first node is further configured to send the query to thesecond node. The second node is configured to operate in thecommunications network. The query is configured to request theinformation on the location of the communication device. Thecommunication device is configured to operate in the communicationsnetwork. The communication device is configured to be identified by thefirst node as a constrained communication device lacking the capabilityto query the second node. The first node is further configured to obtainthe information from the second node, in response to the queryconfigured to be sent. The first node is further configured to initiateupdating the object in the communication device based on the informationconfigured to be obtained.

According to a fourth aspect of embodiments herein, the object isachieved by the communication device, configured to operate in thecommunications network. The communication device is a constrainedcommunication device. The communication device is further configured tosend, to the first node configured to operate in the communicationsnetwork, the indication that the communication device is a constrainedcommunication device. The communication device is also configured toobtain, from the first node and based on to the indication configured tobe sent, the update in the object in the communication device. Theupdate is configured to comprise the information on the location of thecommunication device. The communication device lacks the capability toquery the second node. The second node is configured to operate in thecommunications network and is also configured to have access to thelocation information. The information in the update configured to beobtained is configured to originate in the second node.

According to a fifth aspect of embodiments herein, the object isachieved by a computer program, comprising instructions which, whenexecuted on at least one processor, cause the at least one processor tocarry out the method performed by the wireless device.

According to a sixth aspect of embodiments herein, the object isachieved by a computer-readable storage medium, having stored thereonthe computer program, comprising instructions which, when executed on atleast one processor, cause the at least one processor to carry out themethod performed by the wireless device.

According to a seventh aspect of embodiments herein, the object isachieved by a computer program, comprising instructions which, whenexecuted on at least one processor, cause the at least one processor tocarry out the method performed by the network node.

According to an eighth aspect of embodiments herein, the object isachieved by a computer-readable storage medium, having stored thereonthe computer program, comprising instructions which, when executed on atleast one processor, cause the at least one processor to carry out themethod performed by the network node.

By the first node sending the query to the second node on the locationof the communication device, the communication device, in spite of beinga constrained communication device lacking the capability to query thesecond node, is enabled to obtain the information on its location.Therefore, location information is provided to communication devices inscenarios, e.g., IoT scenarios, where obtaining location information byconstrained communication devices is not supported.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of embodiments herein are described in more detail withreference to the accompanying drawings, according to the followingdescription.

FIG. 1 is a schematic diagram illustrating two non-limiting examples ina) and b), respectively, of a communications network, according toembodiments herein.

FIG. 2 is a flowchart depicting embodiments of a method in a first node,according to embodiments herein.

FIG. 3 is a flowchart depicting embodiments of a method in acommunications device, according to embodiments herein.

FIG. 4 is a flowchart depicting embodiments of a method in acommunications network according to embodiments herein.

FIG. 5 is a flowchart depicting embodiments of a SCEF location object,according to embodiments herein.

FIG. 6 is a flowchart depicting embodiments of a Topology Diagram,according to embodiments herein.

FIG. 7 is a schematic block diagram illustrating two non-limitingexamples, a) and b), of a first node, according to embodiments herein.

FIG. 8 is a schematic block diagram illustrating two non-limitingexamples, a) and b), of communication device, according to embodimentsherein.

DETAILED DESCRIPTION

As part of the development of embodiments herein, a problem with exitingmethods will first be identified and discussed.

As explained earlier, in existing methods, the functionality ofconstrained devices to is rather basic, given the limited capabilitiesof these devices. In particular, services that are not accessible toconstrained devices are location services, as these devices usually lackmeans of location, such as Global Positioning System (GPS).

Locations services may be obtained through a 3GPP network. In general,the services provided by a 3GPP network to 3rd party application serversmay be securely exposed via a Service Capability Exposure Function(SCEF). The SCEF may be understood to provide a means to access, such asa REST Application Programming Interface (API), to information about UEsthat may be normally found in a network of an operator, e.g., location,mobility, etc. The 3GPP organization provides a specification fornorthbound APIs that expose UE information, such as relative location,radio properties, roaming, mobility, etc. . . . through well-knownHypertext Transfer Protocol (HTTP) APIs. The T8 APIs define theinteraction between Application Servers (AS) exposing the API, that is,services interested in the SCEF data, and the SCEF, which may store theinformation.

Several embodiments are comprised herein, which address the limitationsof the existing methods. As an overview, embodiments herein may beunderstood to be drawn to providing access to location services toconstrained devices, which lack such capability. In general, embodimentsherein may be understood as relating to SCEF location services overLWM2M. In particular, embodiments herein may be understood to addresshow an LWM2M Server may interface with the SCEF in a network, and fetchthe location of a device that lacks location capabilities, pushing itafterwards to the device.

Embodiments herein are related to an internal implementation documentproviding for energy efficient accurate positioning methods. Suchmethods are related to optimizing GPS positioning to save battery.However, they do not use SCEF or the T8 interface. Embodiments hereincomplement the previous internal implementation document with theinterfaces and LWM2M mechanisms that may be needed.

The embodiments will now be described more fully hereinafter withreference to the accompanying drawings, in which examples are shown. Inthis section, embodiments herein are illustrated by exemplaryembodiments. It should be noted that these embodiments are not mutuallyexclusive. Components from one embodiment or example may be tacitlyassumed to be present in another embodiment or example and it will beobvious to a person skilled in the art how those components may be usedin the other exemplary embodiments.

FIG. 1 depicts two non-limiting examples, in panels “a” and “b”,respectively, of a communications network 10, in which embodimentsherein may be implemented. In some example implementations, such as thatdepicted in the non-limiting example of FIG. 1a ), the communicationsnetwork 10 may be a computer network. In other example implementations,such as that depicted in the non-limiting example of FIG. 1b ), thecommunications network 10 may be implemented in a telecommunicationsnetwork 100, sometimes also referred to as a cellular radio system,cellular network or wireless communications system. In some examples,the telecommunications network 100 may comprise network nodes which mayserve receiving nodes, such as wireless devices, with serving beams.

The telecommunications network 100 may for example be a Narrow-Band IoT(NB-IoT) network, a Category M1 (CATM) network, a Global System forMobile communications (GSM) network, or another Internet serviceprovider (ISP)-oriented network that may support an SCEF.

In some examples, the telecommunications network 100 may for example bea network such as 5G system, or Next Gen network. The telecommunicationsnetwork 100 may also support other technologies, such as a Long-TermEvolution (LTE) network, e.g. LTE Frequency Division Duplex (FDD), LTETime Division Duplex (TDD), LTE Half-Duplex Frequency Division Duplex(HD-FDD), LTE operating in an unlicensed band, Wideband Code DivisionMultiple Access (WCDMA), Universal Terrestrial Radio Access (UTRA) TDD,GSM/Enhanced Data Rate for GSM Evolution (EDGE) Radio Access Network(GERAN) network, Ultra-Mobile Broadband (UMB), EDGE network, networkcomprising of any combination of Radio Access Technologies (RATs) suchas e.g. Multi-Standard Radio (MSR) base stations, multi-RAT basestations etc., any 3rd Generation Partnership Project (3GPP) cellularnetwork, Wireless Local Area Network/s (WLAN) or WiFi network/s,Worldwide Interoperability for Microwave Access (WiMax), IEEE802.15.4-based low-power short-range networks such as IPv6 overLow-Power Wireless Personal Area Networks (6LowPAN), Zigbee, Z-Wave,Bluetooth Low Energy (BLE), or any cellular network or system.

The communications network 10 comprises a plurality of nodes, whereof afirst node 111, and a second node 112 are depicted in FIG. 1. Each ofthe first node 111, and the second node 112 may be understood,respectively, as a first computer system, and a second computer system.The first node 111 may be understood as a server lacking positioningfunctionality itself, but yet able to communicate with the second node112, which may be understood to have positioning functionality. To havepositioning functionality may be understood herein as having thecapability to derive and provide positioning information relating to anode or a communication device in the communications network 10. Thefirst node 111 may be further understood to have a capability tocommunicate with communication devices being constrained devices. Intypical examples, the first node 111 may be a LightWeight Machine toMachine protocol (LWM2M) server. The second node 112 may be understoodto lack the capability to communicate with communication devices beingconstrained devices. In some typical examples, the second node 112 mayoperate a Service Capability Exposure Function (SCEF). In some examples,the second node 112 may support operation on the DNS protocol. In someexamples, the first node 112 may support operation on the CoAP and onthe DNS protocol.

In some examples, any of the first node 111 and the second node 112 maybe implemented, as depicted in the non-limiting example of FIGS. 1a )and 1 b), as a standalone server in e.g., a host computer in the cloud120. Any of the first node 111, and the second node 112 may in someexamples be a distributed node or distributed server, with some of theirrespective functions being implemented locally, e.g., by a clientmanager, and some of its functions implemented in the cloud 120, bye.g., a server manager. Yet in other examples, any of the first node 111and the second node 112 may also be implemented as processing resourcesin a server farm. Any of the first node 111 and the second node 112 maybe under the ownership or control of a service provider, or may beoperated by the service provider or on behalf of the service provider.

The communications network 10 comprises a communication device 130, asdepicted in the non-limiting example scenario of FIG. 1. Thecommunications network 10 may also comprise other communication devices.The communication device 130 may be a UE or a Customer PremisesEquipment (CPE) which may be understood to be enabled to communicatedata, with another entity, such as a server, a laptop, aMachine-to-Machine (M2M) device, device equipped with a wirelessinterface, or any other radio network unit capable of communicating overa wired or radio link in a communications system such as thecommunications network 10. In some embodiments, the communication device130 may be understood to be a constrained device in e.g., an IoTnetwork. In some particular embodiments, the communication device 130may be understood to be a constrained device operating on LWM2M. Thecommunication device 130 may run a client application, which may beenabled to communicate with a host application run by the first node111. The communication device 130 may be understood to lack a capabilityto directly query the second node 112. For example, the communicationdevice 130 may support operation on CoAP, and may be incapable ofsupporting operation on the DNS protocol. Incapable of supporting may beunderstood as lacking support, or not being configured to support, forexample.

The communication device 130 may be a wireless device comprised in thecommunications network 10, such as a Bluetooth Low Energy (BLE) UserEquipment (UE). The communication device 130 may be enabled tocommunicate wirelessly in the communications network 10 and, in someparticular examples, may be able support beamforming transmission. Thecommunication may be performed e.g., via a RAN and possibly one or morecore networks, comprised within the communications network 10.

The communication device 130 may be also e.g., a mobile terminal,wireless terminal and/or mobile station, mobile telephone, cellulartelephone, or laptop, just to mention some further examples. Thecommunication device 130 may be, for example, portable, pocket-storable,hand-held, computer-comprised, a sensor, camera, or a vehicle-mountedmobile device, enabled to communicate voice and/or data, via a RAN, withanother entity, such as a server, a laptop, a Personal Digital Assistant(PDA), or a tablet computer, sometimes referred to as a tablet withwireless capability, or simply tablet, a Machine-to-Machine (M2M)device, a device equipped with a wireless interface, such as a printeror a file storage device, modem, Laptop Embedded Equipped (LEE), LaptopMounted Equipment (LME), USB dongles or any other radio network unitcapable of communicating over a wired or radio link in thecommunications network 10.

The telecommunications network 100 may cover a geographical area which,which in some embodiments may be divided into cell areas, wherein eachcell area may be served by a radio network node 140, although, one radionetwork node may serve one or several cells. In the example of FIG. 1b ,the radio network node 140 serves a cell 150. The radio network node 140may be e.g., a gNodeB. That is, a transmission point such as a radiobase station, for example an eNodeB, or a Home Node B, a Home eNode B orany other network node capable to serve a wireless device, such as auser equipment or a machine type node in the communications network 10.The radio network node 140 may be of different classes, such as, e.g.,macro eNodeB, home eNodeB or pico base station, based on transmissionpower and thereby also cell size. In some examples, the radio networknode may serve receiving nodes with serving beams. The radio networknode 140 may support one or several communication technologies, and itsname may depend on the technology and terminology used. Any of the radionetwork nodes that may be comprised in the communications network 10 maybe directly connected to one or more core networks.

The first node 111 is configured to communicate within thecommunications network 10 with the second node 112 over a first link161, e.g., a radio link, an infrared link, or a wired link. The firstlink 161 may be understood to be comprised of a plurality of individuallinks. The first node 111 is configured to communicate within thecommunications network 10 with the communication device 120 over asecond link 162, e.g., a radio link, an infrared link, or a wired link.The second link 162 may be understood to be comprised of a plurality ofindividual links.

Any of the first link 161 and the second link 162 may be a direct linkor it may go via one or more computer systems or one or more corenetworks in the communications network 10, which are not depicted inFIG. 1, or it may go via an optional intermediate network. Theintermediate network may be one of, or a combination of more than oneof, a public, private or hosted network; the intermediate network, ifany, may be a backbone network or the Internet; in particular, theintermediate network may comprise two or more sub-networks, which is notshown in FIG. 1.

In general, the usage of “first”, “second”, etc. herein may beunderstood to be an arbitrary way to denote different elements orentities, and may be understood to not confer a cumulative orchronological character to the nouns they modify.

Embodiments of method performed by the first node 111 will now bedescribed with reference to the flowchart depicted in FIG. 2. The methodmay be understood to be for handling positioning information. The firstnode 111 operates in the communications network 10. As mentionedearlier, in some embodiments, the first node 111 may be a LightWeightMachine to Machine protocol (LWM2M) server. The first node 111 may run ahost application capable of sharing its resources with a clientapplication run by the communication device 130.

The method may comprise the actions described below. Several embodimentsare comprised herein. In some embodiments some of the actions may beperformed. In some embodiments all the actions may be performed. One ormore embodiments may be combined, where applicable. All possiblecombinations are not described to simplify the description. It should benoted that the examples herein are not mutually exclusive. Componentsfrom one example may be tacitly assumed to be present in another exampleand it will be obvious to a person skilled in the art how thosecomponents may be used in the other examples. In FIG. 2, optionalactions are indicated with dashed boxes.

Action 201

In the course of operations of the communications network 10 the firstnode 111 may, in this Action 201, obtain, from the communication device130, an indication that the communication device 130 is a constrainedcommunication device 130. In some embodiments, the communication device130 may be a constrained device operating on LWM2M. The indication maythen indicate that the communication device 130 is a constrained deviceoperating on LWM2M. The indication may be, for example, a common deviceidentifier, such as a Uniform Resource Name (URN), Uniform ResourceIdentifier (URI), an International Mobile Equipment Identity (IMEI), orsome identity derived from key material, of the communications device130. In some examples, the first node 111 may obtain the indicationduring the course of a Bootstrapping and Registration procedures, ase.g., specified by the Open Mobile Alliance Device Management (OMADM)-LWM2M. The Bootstrapping procedure may be understood to be used toonboard an IoT device into a management system, providing key materialthat may be necessary to establish a secure channel. The registrationprocedure may be understood to allow the manager to know which are theproperties of the device, the measurements it may be able take, when itmay be able to take them, etc. These procedures will be brieflydescribed later.

The obtaining, e.g., receiving, in this Action 201 may be performed,e.g., via the second link 162.

In some embodiments, the first node 111 may further obtain, from thecommunication device 130, either as a part of this Action 201, or as aseparate Action, a query, e.g., a first query, information on thelocation of the communication device 130, that is, the positioninginformation.

Action 202

To be able to receive notifications, publications, of changes, etc. . .. in some embodiments, the first node 111 may, in this Action 202, set asubscription with the second node 112 for the communication device 130.The second node 112 may be understood to operate in the communicationsnetwork 10, and may operate a Service Capability Exposure Function(SCEF). To set a subscription may be understood as a procedure to allowthe first node 111 to to receive notifications, publications, ofchanges, etc. . . . . For example, in CoAP, the procedure is describedin RFC7641.

In some embodiments, the first node 111 may set the subscription basedon having received the first query from the communication device 130.

Action 203

In some examples, based on identifying that the communication device 130is a constrained device, the first node 111 may, e.g., autonomously, orbased on a request or query from the communication device 130, initiatethe provision of location information to the communication device 130.

In preparation for the provision of location information to thecommunication device 130 which may eventually take place, in this Action203, the first node 111 may create an object in the communication device130 as a placeholder for the information on the location of thecommunication device 130. An object may be understood as, for exampledescribed in the Open Mobile Alliance LWM2M v 1.0http://www.openmobilealliance.org/wp/OMNA/LwM2M/LwM2MRegistry.html. Thecreating 203 may be based on the communication device 130 beingidentified by the first node 111 as a constrained communication device130 lacking a capability to query the second node 112. That is, theidentification of the communication device 130 as a constrainedcommunication device may trigger the creation of the object in thecommunication device 130, as the first node 111 may determine it is acommunication device 130 lacking the capability to directly obtain thelocation information itself. For example, LWM2M clients, beinglightweight may often not have a Global Positioning System (GPS) chip inorder to spare some battery.

In some examples, the object may be, e.g., a “3GPP Location” object.Particularly, in some examples herein, the object may be understood as anew LWM2M Object that may partially map to the “LocationInfo” Data typedefined in 3GPP TS 29.122. Such object may be used when other means oflocation, e.g., GPS, may not be available on the device.

Action 204

Having the communication device 130 been identified by the first node111 as a constrained communication device 130 lacking the capability toquery the second node 112, the first node 111, in this Action 204, sendsa query to the second node 112 operating in the communications network10. The query requests information on a location of the communicationdevice 130 operating in the communications network 10.

The second node 112 may be able to provide a rough location of thecommunication device 130, by for example, deriving it by triangulatingthe position of the communication device 130, taken, e.g., from a modemin the communication device 130, with neighboring radio nodes such asthe radio network node 140.

The sending in this Action 204 may be performed over e.g., the firstlink 161. The queried information may be, for example, an elapsed timesince a last contact of the communication device 130 with thetelecommunications network 100, an identifier of the cell 150 where thecommunication device 130 is registered, an identifier of the radionetwork node 140 which is currently serving or in proximity of thecommunication device 130, an identifier of geographic information aboutthe communication device 130, a latitude value, an identity of the areawhere the communication device 130 is located, a longitude value, anidentifier of a routing area where the communication device 130 islocated, an identifier of a service area the communication device 130 islocated, an identifier of a tracking area where the communication device130 is located, etc. . . . .

In some examples, the first node 111 may send the query to the secondnode 112, based on, e.g., triggered by, the first query received fromthe communication device 130. The query sent from the first node 111 tothe second node 112 may then be considered a second query.

Action 205

The first node 111 may then, in this Action 205, obtain the informationfrom the 20 second node 112, in response to the sent query. In exampleswherein the second node 112 may operate a SCEF, the information may beobtained, in the form of “Notification Data”. A particular example ofthe information that may be obtained will be provided later in FIG. 6.

The obtaining, e.g., receiving, in this Action 205 may be performed overe.g., the first link 161.

Action 206

The obtained information may be based on one or more first capabilitiesto process information of the first node 111 and the second node 112.That is, the information may be obtained by the first node 111 in aformat that both the first node 111 and the second node 112 may support.For example, the one or more first capabilities to process informationmay be the support of the Domain Name System (DNS) protocol. Since thecommunication device 130 is a constrained device, with very limitedresources, it may lack the one or more first capabilities to processinformation. For example, the communication device 130 may lack supportof the DNS protocol. The communication device 130 may instead have oneor more second capabilities to process information. For example, the oneor more second capabilities to process information may be the support ofthe Constrained Application Protocol (CoAP) protocol. Therefore, in thisAction 206, the first node 111 may adapt the obtained information to theone or more second capabilities to process information of thecommunication device 130, rendering the adapted obtained informationcompatible with the one or more second capabilities to process theinformation of the communication device 130. That is, the obtainedinformation may be adapted into a format that both the first node 111and the communication device 130 may support.

The adapting in this Action 206 may comprise, for example, modifying aformat in which the information may have been obtained from the secondnode 112, e.g., JavaScript Object Notation (JSON), and which thecommunication device 130 may not be able to process, into another formatthe communication device 130 may be able to process, such as, e.g.,Sensor Markup Language (SENML), Concise Binary Object Representation(CBOR), or JSON, in cases the information is obtained in a format otherthan JSON.

Action 207

The first node 111 may then, in this Action 207, initiate updating theobject in the communication device 130 based on the obtainedinformation. The object may be understood to be the created object inAction 202. Updating may be understood as writing the obtainedinformation in the object. The format of the message payload may beSENML, CBOR or JSON. In other words, in this Action 207, the first node111 may provide the location information to the communications device130.

To initiate updating may be understood as to begin updating itself, orto trigger the updating by a different node, e.g., in a distributed nodeenvironment. The updating in this Action 207 may be performed over e.g.,the second link 162.

In some embodiments, the adaption of the obtained information in Action206 may have been performed prior to the initiating updating of theobject in this Action 207. In such embodiments wherein Action 206 mayhave been performed, the object may be updated, in this Action 207, withthe adapted information, thereby enabling the communication device 130to process the updated information.

Action 208

In some embodiments, the first node 111 may have set the subscription inAction 202 prior to the initiating updating of the object in Action 207.The first node 111 may at some subsequent time point, obtain, in thisAction 208, from the second node 112 and based on the set subscription,additional information on the location of the communication device 130.This may occur, for example, after a change in the location of thecommunication device 130 may have been detected.

The obtaining, e.g., receiving, in this Action 208 may be performed overe.g., the first link 161.

Action 209

The first node 111 may then, in this Action 209, update the object inthe communication device 130 based on the obtained additionalinformation. As described before, the additional information may havebeen obtained according to the one or more first capabilities of thefirst node 111 and the second node 112, and therefore, the obtainedadditional information may be also processed according to the one ormore second capabilities of the communication device 130.

The updating in this Action 207 may be performed over e.g., the secondlink 162.

In some embodiments, the obtained additional information comprises anindication of an age of the information on the location of thecommunication device 130. This may allow the estimation by thecommunication device 130 of its sleep and movement patterns.

Embodiments of a method performed by the communication device 130, willnow be described with reference to the flowchart depicted in FIG. 3. Themethod may be understood to be for handling positioning information. Thecommunication device 130 operates in the communications network 10. Asmentioned earlier, in some embodiments, the communication device 130 isa constrained device. The communication device 130 may run a clientapplication capable of requesting resources or services from a hostapplication run by the first node 111.

The method may comprise one or more of the following actions. Severalembodiments are comprised herein. In some embodiments all the actionsmay be performed. One or more embodiments may be combined, whereapplicable. All possible combinations are not described to simplify thedescription. It should be noted that the examples herein are notmutually exclusive. Components from one example may be tacitly assumedto be present in another example and it will be obvious to a personskilled in the art how those components may be used in the otherexamples. In FIG. 3, optional actions are indicated with dashed boxes.

The detailed description of some of the following corresponds to thesame references provided above, in relation to the actions described forthe first node 111, and will thus not be repeated here to simplify thedescription. For example, the first node 111 may be a LWM2M server.

Action 301

In this Action 301, the communication device 130 sends, to the firstnode 111 operating in the communications network 10, the indication thatthe communication device 130 is a constrained communication device 130,which indication was described earlier. As also described earlier, insome examples, the communication device 130 may send the indicationduring the course of a Bootstrapping and Registration procedures, ase.g., specified by the OMA DM-LWM2M.

The sending in this Action 301 may be performed, e.g., via the secondlink 162.

Action 302

In some embodiments, the communication device 130 may, in this Action302, send, to the first node 111, the query, that is, the first query,requesting the information on the location of the communication device130.

The sending in this Action 302 may be performed, e.g., via the secondlink 162.

Action 303

The communication device 130 may then, in this Action 303, obtain, fromthe first node 111, the object in the communication device 130 as aplaceholder for the information on the location of the communicationdevice 130.

The obtaining, e.g., receiving, in this Action 303 may be performed overe.g., the 30 second link 162.

Action 304

In this Action 304, the communication device 130 obtains, from the firstnode 111 and based on to the sent indication in Action 301, the updatein the object in the communication device 130. The update comprises theinformation on the location of the communication device 130. Asexplained earlier, the communication device 130 lacks the capability toquery the second node 112 operating in the communications network 10having access to the location information. The information in theobtained update originates in the second node 112. As stated earlier, insome embodiments, the second node 112 may operate a SCEF.

In some embodiments wherein the communication device 130 has sent thefirst query in Action 302, the obtained update in this Action 304 may bebased on the sent query.

The obtaining, e.g., receiving, in this Action 304 may be performed overe.g., the 10 second link 162.

The update may be obtained according to the one or more secondcapabilities to process the information of the communication device 130.

In some embodiments, the obtained information may comprise theindication of the age of the information on the location of thecommunication device 130.

Action 305

In this Action 305, the communication device 130 obtains, from the firstnode 111, and based on the set subscription with the second node 112 forthe communication device 130, the other update in the object in thecommunication device 130 with the additional information on the otherlocation of the communication device 130. The additional information mayoriginate from the second node 112.

The obtaining, e.g., receiving, in this Action 305 may be performed overe.g., the second link 162.

FIG. 4 is a schematic diagram illustrating a non-limiting example of thegeneral topology of the communications network 10 wherein embodimentsherein may be implemented. As a constrained device, the communicationdevice 130 may be managed and provided with services through the LWM2Mprotocol. LWM2M uses a LWM2M server and client system. In thenon-limiting example of FIG. 4, the first node 111 is an LWM2M Serverrunning a host application, and the communication device 130 runs aLWM2M Client application 401. In FIG. 4, the communication device 130denoted as “Device”, is running LWM2M and is connected with a modem 402,e.g., a 3GPP type of modem, such as NB-IoT, LTE, GSM . . . , to thetelecommunications network 100, which is in this example a 3GPP network.The telecommunications network 100 supports the 35 second node 112,which is here an SCEF. The telecommunications network 100 comprises alsoa Mobility Management Entity (MME) 400. As stated earlier, LWM2Mclients, being lightweight, may often not have a GPS chip, in order tospare some battery. However the SCEF may take at 410, a rough locationfrom the modem in the communication device 130 by triangulating theposition with the base stations surrounding it. While the communicationdevice 130 may lack an ability to directly obtain that position from theSCEF, the position may be accessible from the SCEF and may be sent tothe communication device 130 via the LWM2M server. The communicationdevice 130 may send the indication that it is a constrained device tothe first node 111 at 301, as indicated by “UE Info” in the Figure. Thefirst device 111 may receive the indication according to Action 201. Thefirst node 111 may send the query to the second node 112 according toAction 204, and may then obtain the information from the second node112, according to Action 205. The first node 111 may then send thelocation to the communication device 130 according to Action 207, whichthe communication device 130 obtains according to Action 304.

The methods just described as being implemented by the first node 111and the second node 112 will now be described in further detail next, inrelation to FIG. 5, with a particular non-limiting example, wherein thegeneral process of embodiments herein is tied to the LWM2M DeviceManagement interface. New operations according to embodiments herein areindicated with the symbol “*”. FIG. 5 is a schematic diagramillustrating a non-limiting example of the methods that may be performedby the first node 111, which is an LWM2M Server “LS”, and CoAP Client,in the non-limiting example of FIG. 5, and the communication device 130,which is a LWM2M Client “LC” in the non-limiting example of FIG. 5. Inthe non-limiting example in FIG. 5, the LC is a constrained device onthe telecommunication network 100, which is a 3GPP network comprisingthe second node 112, an SCEF in the non-limiting example of FIG. 5.

At 501 may start to perform a LWM2M Bootstrapping and Registrationprocedures as specified by the OMA DM-LWM2M. As part of theseprocedures, the communication device 130 sends, according to Action 301,the indication that the communication device 130 is a constrainedcommunication device 130 in a Bootstrap Request. The Bootstrap Requesttargets a Bootstrap Server 500. The indication in this case is an EndPoint (EP) Name, which may be an IMEI. The LWM2M Bootstrapping andRegistration procedures may also comprise, at 502, configuring theclient, deleting objects and creating LM2M objects in order toinitialize the device towards the management system. At 503, theBootstrapping and Registration procedures are finished, as indicated bya 2.04 Success, which is a standard REST CoAP Response message when anoperation is successful, as defined in RFC7252. At 504, thecommunication device 130 is then registered with its IMEI on the firstnode 111. The first node 111 then sets an empty “3GPP Location”, whereinempty may be understood to mean that the communication device 130 willhave no location until updated from the first node 111. At 505, thecommunication device 130 registers on the first node 111 with its IMEI.At 506, the first node 111 acknowledges that the communication device130 is successfully registered, providing the registration handler. At507*, in accordance with Action 203, the first node 111 creates an empty“Location Object” in the communication device 130 as a placeholder forthe location fetched later on from the second node 112, that is, theSCEF. At 508*, the first node 111 uses the UE information, e.g., IMSI,IMEI, received during the registration to query the second node 112 overthe T8 interface for getting the location information of thecommunication device 130, in accordance with Action 204. The first node111 sets a WebsockNotifConfig for that information, to get notified forthe delivery of notifications over Websockets for the IMEI of thecommunication device 130. At 509*, the notification arrives from thesecond node 112 in the form of “Notification Data”, in accordance withAction 205, and based on the IMEI. At 510*, the first node 111 uses thelocation information from the second node 112 to update the “LocationObject” for the communication device 130, in accordance with Action 207,and based on the IMEI. The updating is performed via a “PUT” action. At511, the communication device 130 logic may now change depending on thelocation, i.e., actuate only in this area take measurements on thatarea, etc, independent from GPS. At 512*, the first node 111 writes thenew object on the communication device 130, applications using LWM2M, orCoAP, and may now be able to use location information directly from thecommunication device 130. At 512*, whenever a new notification comesfrom the second node 112, the first node 111 acts as a proxy towards thecommunication device 130 and, in accordance with Action 208, update itaccordingly.

FIG. 6 is a schematic diagram illustrating a particular non-limitingexample of the information on the location of the communication device130 that may be obtained by the first node 111 from the second node 112,as provided by different indicators. As depicted in the figure, theinformation may comprise: an elapsed time since a last network contactof the communication device 130, indicated by an “ageOLocationInfo”value; a Cell Global Identification identifying a cell where thecommunication device 130 is registered, indicated by a “Cell ID” value;an eNodeB in which the communication device 130 is currently located,indicated by a “enodeBld” value; an identifier of geographic informationabout the communication device 130, indicated by a “geographicArea”value, a latitude value, indicated by a “latitude” value; a LocationArea Identity where the communication device 130 is located, indicatedby a “locationAreaId” value; a longitude value, indicated by a“longitude” value; a Routing Area Identity where the communicationdevice 130 is located, indicated by a “routingAreaId” value; a ServiceArea Identity where the communication device 130 is located, indicatedby a “serviceAreaId” value; a Tracking Area Identity where thecommunication device 130 is located, indicated by a “trackingAreaId”value.

As a general summarized overview of the foregoing, embodiments hereinmay be understood to provide a mechanism for providing location to adevice over LWM2M, when the network supports SCEF and may provide roughlocation settings.

Some embodiments herein, particularly, may be understood to provide anew LWM2M Object that partially maps to the “LocationInfo” Data typedefined in 3GPP TS 29.122. Such object may be used when other means oflocation, e.g., GPS, are not available on the device. Embodiments hereinmay be understood to describe a simple REST API to interact with thatObject in the SCEF, as well as the mechanism that may be required tointeract with the device.

One advantage of embodiments herein is that they allow LWM2M to providelocation services to devices, such as the communication device 130. Afurther advantage of embodiments herein is that they make use ofstandard 3GPP, OMA and Internet Engineering Task Force (IETF) protocols.Yet another advantage of embodiments herein is that they do not need newlogic on devices, that is, further multiple stacks are not needed on theconstrained device to obtain the location. Having access to the firstnode 111 may be understood to be enough. Another advantage ofembodiments herein is that, although accuracy may vary, they enable topinpoint the location of a device to the closest eNodeB. A furtheradvantage of embodiments herein is that they also enable to provide theage of the location information, allowing to estimate sleep and movementpatterns of the communication device 130, which may then be used tobetter integrate the network on the application software systems of thecommunication device 130. For example, it may be used to learn about theinteractions of the communication device 130 with the environment, whenit is connected, when it is off and where it is normally geographicallylocated.

FIG. 7 depicts two different examples in panels a) and b), respectively,of the arrangement that the first node 111 may comprise to perform themethod actions described above in relation to FIG. 2. The first node 111is configured to operate in the communications network 10.

The detailed description of some of the following corresponds to thesame references provided above, in relation to the actions described forthe first node 111, and will thus not be repeated here. For example, thefirst node 111 may be an LWM2M server. In FIG. 7, optional units areindicated with dashed boxes.

In some embodiments, the first node 111 may comprise the followingarrangement depicted in FIG. 7 a.

The first node 111 is configured to, e.g. by means of a sending unit 701within the first node 111 configured to, send the query to the secondnode 112 configured to operate in the communications network 10. Thequery is configured to request the information on the location of thecommunication device 130 configured to operate in the communicationsnetwork 10. The communication device 130 is configured to be identifiedby the first node 111 as a constrained communication device 130 lackingthe capability to query the second node 112.

As described earlier, in some embodiments, the second node 112 isconfigured to operate an SCEF.

In some embodiments, the communication device 130 may be a constraineddevice configured to operate on LWM2M.

The first node 111 is also configured to, e.g. by means of an obtainingunit 702 within the first node 111 configured to, obtain the informationfrom the second node 112, in response to the query configured to besent.

In some embodiments, the first node 111 is further configured to, e.g.by means of an initiating unit 703 within the first node 111 configuredto, initiate updating the object in the communication device 130 basedon the information configured to be obtained.

In some embodiments, the first node 111 may be configured to, e.g. bymeans of a creating unit 704 within the first node 111 configured to,create the object in the communication device 130 as the placeholder forthe information on the location of the communication device 130. Tocreate may be configured to be based on the communication device 130being identified by the first node 111 as a constrained communicationdevice 130 lacking the capability to query the second node 112.

In some embodiments, the information configured to be obtained may beconfigured to be based on the one or more first capabilities to processinformation of the first node 111 and the second node 112. In suchembodiments, the first node 111 may be further configured to, prior tothe updating of the object, e.g. by means of an adapting unit 705 withinthe first node 111 configured to, adapt the information configured to beobtained to the one or more second capabilities to process informationof the communication device 130, and render the information configuredto be obtained and adapted compatible with the one or more secondcapabilities to process the information of the communication device 130.In some of such embodiments, the object may be further configured to beupdated with the information configured to be adapted.

In some embodiments, the first node 111 may be further configured to,e.g. by means of the obtaining unit 702 within the first node 111configured to, obtain, from the communication device 130, the indicationthat the communication device 130 is a constrained communication device130.

In some embodiments, the first node 111 may be further configured to,e.g. by means of a setting unit 706 within the first node 111 configuredto, set, prior to the updating of the object, the subscription with thesecond node 112 for the communication device 130.

In some embodiments, the first node 111 may be further configured to,e.g. by means of the obtaining unit 702 within the first node 111configured to, obtain, from the second node 112 and based on the setsubscription, the additional information on the location of thecommunication device 130.

In some embodiments, the first node 111 may be further configured to,e.g. by means of an updating unit 707 within the first node 111configured to, update the object in the communication device 130 basedon the obtained additional information. The obtained additionalinformation may be configured to be processed according to the one ormore second capabilities of the communication device 130.

The additional information configured to be obtained may comprise theindication of the age of the information on the location of thecommunication device 130.

The embodiments herein may be implemented through one or moreprocessors, such as a processor 708 in the first node 111 depicted inFIG. 7a , together with computer program code for performing thefunctions and actions of the embodiments herein. The processor 708 maybe understood herein to be a hardware component. The program codementioned above may also be provided as a computer program product, forinstance in the form of a data carrier carrying computer program codefor performing the embodiments herein when being loaded into the in thefirst node 111. It is however feasible with other data carriers such asa memory stick. The computer program code may furthermore be provided aspure program code on a server and downloaded to the first node 111.

The first node 111 may further comprise a memory 709 comprising one ormore memory units. The memory 709 is arranged to be used to storeobtained information, store data, configurations, schedulings, andapplications etc. to perform the methods herein when being executed inthe first node 111.

In some embodiments, the first node 111 may receive information from,e.g., the second node 112 and the communication device 130, through areceiving port 710. In some examples, the receiving port 710 may be, forexample, connected to one or more antennas in first node 111. In otherembodiments, the first node 111 may receive information from anotherstructure in the communications network 10 through the receiving port710. Since the receiving port 710 may be in communication with theprocessor 708, the receiving port 710 may then send the receivedinformation to the processor 708. The receiving port 710 may also beconfigured to receive other information.

The processor 708 in the first node 111 may be further configured totransmit or send information to e.g., the second node 112 and thecommunication device 130, through a sending port 711, which may be incommunication with the processor 708, and the memory 709.

Any of the sending unit 701, the obtaining unit 702, the initiating unit703, the creating unit 704, the adapting unit 705, the setting unit 706and the updating unit 707 may be the processor 708 of the first node111, or an application running on such processor.

Those skilled in the art will also appreciate that the sending unit 701,the obtaining unit 702, the initiating unit 703, the creating unit 704,the adapting unit 705, the setting unit 706 and the updating unit 707described above may refer to a combination of analog and digitalcircuits, and/or one or more processors configured with software and/orfirmware, e.g., stored in memory, that, when executed by the one or moreprocessors such as the processor 708, perform as described above. One ormore of these processors, as well as the other digital hardware, may beincluded in a single Application-Specific Integrated Circuit (ASIC), orseveral processors and various digital hardware may be distributed amongseveral separate components, whether individually packaged or assembledinto a System-on-a-Chip (SoC).

Thus, the methods according to the embodiments described herein for thefirst node 111 may be respectively implemented by means of a computerprogram 712 product, comprising instructions, i.e., software codeportions, which, when executed on at least one processor 708, cause theat least one processor 708 to carry out the actions described herein, asperformed by the first node 111. The computer program 712 product may bestored on a computer-readable storage medium 713. The computer-readablestorage medium 713, having stored thereon the computer program 712, maycomprise instructions which, when executed on at least one processor708, cause the at least one processor 708 to carry out the actionsdescribed herein, as performed by the first node 111. In someembodiments, the computer-readable storage medium 713 may be anon-transitory computer-readable storage medium, such as memory stick,or stored in the cloud space. In other embodiments, the computer program712 product may be stored on a carrier containing the computer program,wherein the carrier is one of an electronic signal, optical signal,radio signal, or the computer-readable storage medium 713, as describedabove.

The first node 111 may comprise an interface unit to facilitatecommunications between the first node 111 and other nodes or devices,e.g., the second node 112. In some particular examples, the interfacemay, for example, include a transceiver configured to transmit andreceive radio signals over an air interface in accordance with asuitable standard.

In other embodiments, the first node 111 may comprise the followingarrangement depicted in FIG. 7b . The first node 111 may comprise aprocessing circuitry 708, e.g., one or more processors such as theprocessor 708, in the first node 111 and the memory 709. The first node111 may also comprise a radio circuitry 714, which may comprise e.g.,the receiving port 710 and the sending port 711. The processingcircuitry 708 may be configured to, or operable to, perform the methodactions according to FIG. 2 and/or FIG. 5, in a similar manner as thatdescribed in relation to FIG. 7a . The radio circuitry 714 may beconfigured to set up and maintain at least a wireless connection withthe communication device 130. Circuitry may be understood herein as ahardware component.

Hence, embodiments herein also relate to the first node 111 operative tooperate in the communications network 10. The first node 111 maycomprise the processing circuitry 708 and the memory 709, said memory709 containing instructions executable by said processing circuitry 708,whereby the first node 111 is further operative to perform the actionsdescribed herein in relation to the first node 111, e.g., in FIG. 2and/or FIG. 5.

FIG. 8 depicts two different examples in panels a) and b), respectively,of the arrangement that the communication device 130 may comprise toperform the method actions described above in relation to FIG. 3. Thecommunication device 130 is configured to operate in the communicationsnetwork 10. The communication device 130 is a constrained communicationdevice 130. In FIG. 8, optional units are indicated with dashed boxes.

In some embodiments, the communication device 130 may comprise thefollowing arrangement depicted in FIG. 8 a.

The detailed description of some of the following corresponds to thesame references provided above, in relation to the actions described forthe communication device 130, and will thus not be repeated here. Forexample, the communication device 130 may be a constrained deviceconfigured to operate on LWM2M.

The communication device 130 is configured to, e.g. by means of asending unit 801 within the communication device 130 configured to,send, to the first node 111 configured to operate in the communicationsnetwork 10, the indication that the communication device 130 is aconstrained communication device 130.

The communication device 130 is also configured to, e.g. by means of anobtaining unit 802 within the communication device 130 configured to,obtain, from the first node 111 and based on to the indicationconfigured to be sent, the update in the object in the communicationdevice 130. The update is configured to comprise the information on thelocation of the communication device 130. The communication device 130lacks the capability to query the second node 112 configured to operatein the communications network 10 and configured to have access to thelocation information. The information in the update configured to beobtained is configured to originate in the second node 112.

In some embodiments, the first node 111 may be an LWM2M server.

The second node 112 may be configured to operate a SCEF.

In some embodiments, the communication device 130 may be configured to,e.g. by means of the sending unit 801 within the communication device130 configured to, send, to the first node 111, the query requesting theinformation on the location of the communication device 130. The updateconfigured to be obtained may be configured to be based on the sentquery.

In some embodiments, the communication device 130 may be configured to,e.g. by means of the obtaining unit 802 within the communication device130 configured to, obtain, from the first node 111, the object in thecommunication device 130 as the placeholder for the information on thelocation of the communication device 130.

The update may be configured to be obtained according to the one or moresecond capabilities to process the information of the communicationdevice 130.

In some embodiments, the communication device 130 may be configured to,e.g. by means of the obtaining unit 802 within the communication device130 configured to, obtain, from the first node 111 and based on thesubscription for the communication device 130 configured to be set withthe second node 112, the other update in the object in the communicationdevice 130 with the additional information on the other location of thecommunication device 130. The additional information is configured tooriginate from the second node 112.

The information configured to be obtained may be configured to comprisethe indication of the age of the information on the location of thecommunication device 130.

The embodiments herein may be implemented through one or moreprocessors, such as a processor 803 in the communication device 130depicted in FIG. 8, together with computer program code for performingthe functions and actions of the embodiments herein. The processor 803may be understood herein to be a hardware component. The program codementioned above may also be provided as a computer program product, forinstance in the form of a data carrier carrying computer program codefor performing the embodiments herein when being loaded into the in thecommunication device 130. One such carrier may be the cloud 120. It ishowever feasible with other data carriers such as a memory stick. Thecomputer program code may furthermore be provided as pure program codeon a server and downloaded to the communication device 130.

The communication device 130 may further comprise a memory 804comprising one or more memory units. The memory 804 is arranged to beused to store obtained information, store data, configurations,schedulings, and applications etc. to perform the methods herein whenbeing executed in the communication device 130.

In some embodiments, the communication device 130 may receiveinformation from, e.g., the first node 111, through a receiving port805. In some examples, the receiving port 805 may be, for example,connected to one or more antennas in the communication device 130. Inother embodiments, the communication device 130 may receive informationfrom another structure in the communications network 10 through thereceiving port 805. Since the receiving port 805 may be in communicationwith the processor 803, the receiving port 805 may then send thereceived information to the processor 803. The receiving port 805 mayalso be configured to receive other information.

The processor 803 in the communication device 130 may be furtherconfigured to transmit or send information to e.g., the first node 111,through a sending port 806, which may be in communication with theprocessor 803, and the memory 804.

Any of the sending unit 801 and the obtaining unit 802 may be theprocessor 803 of the first node 111, or an application running on suchprocessor.

Those skilled in the art will also appreciate that the sending unit 801and the obtaining unit 802 described above may refer to a combination ofanalog and digital circuits, and/or one or more processors configuredwith software and/or firmware, e.g., stored in memory, that, whenexecuted by the one or more processors such as the processor 803,perform as described above. One or more of these processors, as well asthe other digital hardware, may be included in a singleApplication-Specific Integrated Circuit (ASIC), or several processorsand various digital hardware may be distributed among several separatecomponents, whether individually packaged or assembled into aSystem-on-a-Chip (SoC).

Thus, the methods according to the embodiments described herein for thecommunication device 130 may be respectively implemented by means of acomputer program 807 product, comprising instructions, i.e., softwarecode portions, which, when executed on at least one processor 803, causethe at least one processor 803 to carry out the actions describedherein, as performed by the communication device 130. The computerprogram 807 product may be stored on a computer-readable storage medium808. The computer-readable storage medium 808, having stored thereon thecomputer program 807, may comprise instructions which, when executed onat least one processor 803, cause the, at least, one processor 803 tocarry out the actions described herein, as performed by thecommunication device 130. In some embodiments, the computer-readablestorage medium 808 may be a non-transitory computer-readable storagemedium, such as a memory stick, or stored in the cloud space. In otherembodiments, the computer program 807 product may be stored on a carriercontaining the computer program, wherein the carrier is one of anelectronic signal, optical signal, radio signal, or thecomputer-readable storage medium 808, as described above.

The communication device 130 may comprise an interface unit tofacilitate communications between the communication device 130 and othernodes or devices, e.g., the first node 111. In some particular examples,the interface may, for example, include a transceiver configured totransmit and receive radio signals over an air interface in accordancewith a suitable standard.

In other embodiments, the communication device 130 may comprise thefollowing arrangement depicted in FIG. 8b . The communication device 130may comprise a processing circuitry 803, e.g., one or more processorssuch as the processor 803, in the communication device 130 and thememory 804. The communication device 130 may also comprise a radiocircuitry 809, which may comprise e.g., the receiving port 805 and thesending port 806. The processing circuitry 803 may be configured to, oroperable to, perform the method actions according to FIG. 3 and/or FIG.5, in a similar manner as that described in relation to FIG. 8a . Theradio circuitry 809 may be configured to set up and maintain at least awireless connection with the first node 111. Circuitry may be understoodherein as a hardware component.

Hence, embodiments herein also relate to the communication device 130operative to operate in the communications network 10. The communicationdevice 130 may comprise the processing circuitry 803 and the memory 804,said memory 804 containing instructions executable by said processingcircuitry 803, whereby the communication device 130 is further operativeto perform the actions described herein in relation to the communicationdevice 130, e.g., in FIG. 3 and/or FIG. 5.

When using the word “comprise” or “comprising”, it shall be interpretedas non-limiting, i.e. meaning “consist at least of”.

The embodiments herein are not limited to the above described preferredembodiments. Various alternatives, modifications and equivalents may beused. Therefore, the above embodiments should not be taken as limitingthe scope of the invention.

As used herein, the expression “in some embodiments” has been used toindicate that the features of the embodiment described may be combinedwith any other embodiment or example disclosed herein.

As used herein, the expression “in some examples” has been used toindicate that the features of the example described may be combined withany other embodiment or example disclosed herein.

REFERENCES

-   1. SCEF T8 Specification, 3GPP TS 29.122, V0.54.0    http://ftp.3gpp.org//Specs/archive/29_series/29.122/29122-050.zip.-   2. RFC7252.-   3. LWM2M    (http://www.openmobilealliance.org/release/LightweightM2M/V1_0_1-20170704-A/OMA-TS-LightweightM2M-V1_0_1-20170704-A.pdf).

1-40. (canceled)
 41. A method performed by a first node operating in acommunications network, the method comprising the first node: sending aquery to a second node operating in the communications network, thequery requesting information on a location of a communication deviceoperating in the communications network, wherein the communicationdevice is identified by the first node as a constrained communicationdevice lacking a capability to query the second node; obtaining theinformation from the second node, in response to the sent query; andinitiating updating an object in the communication device based on theobtained information.
 42. The method of claim 41, wherein the first nodeis a LightWeight Machine to Machine Protocol (LWM2M) server.
 43. Themethod of claim 41, wherein the second node operates a ServiceCapability Exposure Function (SCEF).
 44. The method of claim 41, whereinthe communication device is a constrained device operating onLightWeight Machine to Machine Protocol (LWM2M).
 45. The method of claim41, further comprising: creating an object in the communication deviceas a placeholder for the information on the location of thecommunication device, wherein the creating is based on the communicationdevice being identified by the first node as a constrained communicationdevice lacking a capability to query the second node.
 46. The method ofclaim 45: wherein the obtained information is based on one or more firstcapabilities to process information of the first node and the secondnode; and wherein the method further comprises, prior to updating of theobject, adapting the obtained information to one or more secondcapabilities to process information of the communication device,rendering the adapted obtained information compatible with the one ormore second capabilities to process the information of the communicationdevice; and wherein the object is updated with the adapted information.47. The method of claim 41, further comprising obtaining, from thecommunication device, an indication that the communication device is aconstrained communication device.
 48. The method of claim 46, furthercomprising: setting, prior to the updating of the object, a subscriptionwith the second node for the communication device; obtaining, from thesecond node and based on the set subscription, additional information onthe location of the communication device; and updating the object in thecommunication device based on the obtained additional information,wherein the obtained additional information is processed according toone or more second capabilities of the communication device.
 49. Themethod of claim 41, wherein the obtained additional informationcomprises an indication of an age of the information on the location ofthe communication device.
 50. A method performed by a communicationdevice operating in a communications network, the communication devicebeing a constrained communication device, the method comprising thecommunication device: sending, to a first node operating in thecommunications network, an indication that the communication device is aconstrained communication device; and obtaining, from the first node andbased on to the sent indication, an update in an object in thecommunication device, the update comprising information on a location ofthe communication device; wherein the communication device lacks acapability to query a second node operating in the communicationsnetwork having access to the location information; the information inthe obtained update originating in the second node.
 51. The method ofclaim 50, wherein the first node is a LightWeight Machine to MachineProtocol (LWM2M) server.
 52. The method of claim 50, wherein the secondnode operates a Service Capability Exposure Function, SCEF.
 53. Themethod of claim 50, wherein the communication device is a constraineddevice operating on LightWeight Machine to Machine Protocol (LWM2M). 54.The method of claim 50, further comprising sending, to the first node, aquery requesting the information on the location of the communicationdevice; wherein the obtained update is based on the sent query.
 55. Themethod of claim 50, further comprising obtaining, from the first node,the object in the communication device as a placeholder for theinformation on the location of the communication device.
 56. The methodof claim 50, wherein the update is obtained according to one or moresecond capabilities to process the information of the communicationdevice.
 57. The method of claim 50, further comprising obtaining, fromthe first node and based on a set subscription with the second node forthe communication device, another update in the object in thecommunication device with additional information on another location ofthe communication device; the additional information originating fromthe second node.
 58. The method of claim 50, wherein the obtainedinformation comprises an indication of an age of the information on thelocation of the communication device.
 59. A first node configured tooperate in a communications network, the first node comprising:processing circuitry; memory containing instructions executable by theprocessing circuitry whereby the first node is operative to: send aquery to a second node configured to operate in the communicationsnetwork, the query being configured to request information on a locationof a communication device configured to operate in the communicationsnetwork; wherein the communication device is configured to be identifiedby the first node as a constrained communication device lacking acapability to query the second node; obtain the information from thesecond node, in response to the sent query; and initiate updating anobject in the communication device based on the obtained information.60. A communication device configured to operate in a communicationsnetwork, the communication device being a constrained communicationdevice, the communication device being further configured to: processingcircuitry; memory containing instructions executable by the processingcircuitry whereby the communication device is operative to: send, to afirst node configured to operate in the communications network, anindication that the communication device is a constrained communicationdevice; and obtain, from the first node and based on to the indicationconfigured to be sent, an update in an object in the communicationdevice, the update being comprising information on a location of thecommunication device; wherein the communication device lacks acapability to query a second node configured to operate in thecommunications network and configured to have access to the locationinformation; the information in the obtained update originating in thesecond node.